Electronics Initialization
This is a plain-language walkthrough of what happens when a tool's electronics are initialized during service or replacement. Initialization writes the tool's identity — its board ID (MPBID), passwords, Born-On-Date, and security certificates — so the tool is registered and recognized in the Milwaukee OneKey system.
Key Concepts
| Term | Description |
|---|---|
| MPBID | A hex string that uniquely identifies a specific circuit board (e.g. 0229000103) |
| Born-On-Date (BOD) | A timestamp marking when a tool record was provisioned |
| BLE module | The Bluetooth radio on a tool. Older modules carry no unique identity; modern modules support their own unique ID, passwords, and encryption |
| MLS certificates | Security certificates that enable encrypted Bluetooth sessions |
| CANopen | The control protocol used by MX-platform tools (e.g. RollOn), made up of multiple nodes: HMI, BMS, Charger, and Inverter |
| OpenLink | The protocol used by M18 / M12 platform tools |
What the Process Does, Step by Step
1. Look up the tool
The user enters a serial number. The system looks up that tool in OneKey to find its identity and the data it needs to write.
- If a record is found: it gathers the tool's writable data — passwords, Born-On-Date, and security certificates. If the tool has an associated Bluetooth module, it also gathers the module's data.
- If no record is found: the system checks whether the product is even meant to be serialized.
- A non-serializable product simply skips initialization (nothing is wrong; it just doesn't need an identity).
- A serializable product with no record is treated as a failure.
Before moving on, two pre-checks run:
- Outdated Bluetooth firmware check — for certain M18 tools, confirms the Bluetooth module isn't stuck in update mode and isn't running firmware too old to use. If it is, the user is prompted to repair or update it first.
- BMS replacement check — for RollOn tools, detects whether the battery management board (BMS) has been physically swapped for a newer one. If so, a special replacement path is used later.
Once lookup and checks succeed, the tool is ready and the user can start initialization.
2. Choose the right path
How a tool is initialized depends on what kind of tool it is:
- M18 / M12 tools follow the standard initialization path.
- MX / RollOn tools follow the CANopen path, writing identity to each internal node.
- RollOn tools with a replaced BMS follow the BMS replacement path, which provisions a brand-new identity before initializing.
3. Finish up
When the chosen path completes, the tool reports success and any temporary records are cleared. If anything fails along the way, the process reports a failure. Either way, the system resets itself afterward so it's ready for the next tool.
Top-Level Flow
What Gets Written to a Tool
Regardless of the path, initialization writes the same core identity onto the tool's electronics:
- Board ID (MPBID) — the tool's unique identity
- Born-On-Date — when the tool record was provisioned
- Passwords — user, admin, service, and METCO passwords that control access to the tool
- Security certificates — for tools that support encrypted Bluetooth communication
- Ownership claim key — when present, so the tool can be claimed by an owner in OneKey
For tools with a modern Bluetooth module, the same identity is also written to the module so it can be recognized independently. Some tool families get extra finishing steps after the core write — for example resetting a counter, writing tuning parameters, or saving settings to non-volatile memory — but those are tool-specific details on top of the same basic flow.
For a protocol-level walkthrough — the exact read/write order, delays, retries, firmware-version thresholds, and per-node CANopen sequence — see the Technical Reference. It's written so a firmware engineer could reimplement the process without reading the source.